Suppose our trading partner wants a batch of 856s once a day at 9pm.  I set up the batching and schedule, and everything is working.  Now a month from now, we need to redeploy our app.  Do we need to stop the batching orchestration?  As I write this question, I'm thinking maybe not, as the other application is totally independent of the EDI Application. 

What if you we stop the batching orchestration?  Does that cause the batched data to be emitted at that time?

Thanks,
Neal Walters

http://mylifeismymessage.net/overview-of-biztalk-edi-batching/ - I just put together this blog to get a grasp on the EDI batching.  Any comments appreciated.

Hi Neal,

If we stop the running orchestration that will not emit the batched data.

Hi Neal,

For Production deployment of BizTalk Artefacts ,best practise would be to take a down time of your Environment and then stop all incoming message (receive location ) ,outgoing message(send port) ,Orchestration and host instance  of your Environment .

I think you would not like the process where you Message got suspended and it it retrying at port level due to unavailability of another flow inside your farm .This will cause you warning ,error which will be logged into your eventlogs . Even though BizTalk does not leak or emit any messages ,but i would prefer process  should be stopped while I do any short of assembly deployment( Application deployment).

Microsoft has documented some of the best practice for BizTalk Production Environment which is being listed in below MSDN articles .

Production Tasks for BizTalk Application Deployment 

Best Practices for Deploying a BizTalk Application

Hope this answer your question . Any further information if required is always welcomed ..

Thanks
Abhishek

If the EDI Batching instances are completely isolated, mostly meaning that an Agreement does not reference any Send Ports, then no you do not need to change Batching during any Deployment.  If a Send Port is used, you will not be able to remove it which could be a problem depending on the specific Deployment process.

If you Stop a Batching instance, any pending messages will be lost so be sure to Override first.